Repository navigation
ci(release): the release commit no longer counts as a feature, so the next merge does not cut a version of its own - #244
Merged
Conversation
… next merge does not cut a version of its own
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The merged release PR leaves a
feat(release): versioncommit on master, so the next push, even docs or tests only, cut a minor of its own (2.51.0 was such an empty release, and master would now cut 2.53.0).The commit analyzer now gives that commit no release; every other commit keeps the default rules, and the commit message the release workflows look for stays as it is.